As I can see these most of the UseCase classes are useless since it doesn't do any Job rather than calling the repository method itself, which we can directly so by accessing the repository in ViewModel. for e.g take a look into this class.

class ActivateSavingsUseCase(
    private val repository: SavingsAccountActivateRepository
) {
    operator fun invoke(
        savingsAccountId: Int, 
        request: HashMap<String, String>
    ): Flow<DataState<GenericResponse>> = 
        repository.activateSavings(savingsAccountId, request)
}

does it do any extra work rather than calling the method no so it's just useless and anti-pattern and can delete this class and remove overhead.

so my suggestion is to Keep Use Case classes that perform meaningful transformations, business logic, or complex operations. Remove Use Case classes that merely act as pass-through wrappers around repository methods without adding any additional value or processing logic.

Retain Use Cases that:

• Implement complex business rules
• Perform data filtering, sorting, or transformation
• Combine data from multiple repositories
• Add validation or preprocessing steps
• Encapsulate intricate domain-specific logic

Remove Use Cases that:

• Directly delegate to repository methods without any additional processing
• Offer no extra functionality beyond repository method invocation
• Create unnecessary abstraction layers without adding value